BPR Reference Tool 21 CFR Part 111


  


  
  

    

      
      
      
      
    

    

      
0 of 42 reviewed0%

      

    

    

      
      
    

    

  


  
  

    

      
      
      
      
      
      
      
      
    

    

      
      
      
    

    

  


  
  

    


      
How to Use This Tool

      
This tool contains 42 elements drawn from three domains that together define what belongs in a well-designed Batch Production Record. It supports two primary workflows: a design pipeline for building new BPRs and a compliance pipeline for reviewing existing ones.


      

         Regulatory (21 CFR 111)
         Industry Best Practice
         Data Integrity
      


      
The Design Pipeline

      

        Learn
        →
        Template
      

      
Use this sequence when you are building a new BPR or redesigning an existing template.


      
Step 1 — Learn

      
Start here to understand what goes into a BPR and why. Each of the 42 elements is presented as an expandable card. Click a card to reveal its regulatory source, rationale, and implementation guidance.

      
    
        
  • Filter by domain using the colored buttons at the top. Isolate just the regulatory requirements, or focus on data integrity principles. Combine filters freely.
    • 
        
  • Search across all fields — element names, CFR section numbers, keywords like "label" or "traceability," or concepts like "ALCOA."
    • 
        
  • Read the rationale. This is the most important field. A designer who understands why a requirement exists will make better judgment calls when adapting the template to a specific product or process.
    • 
      


      
Step 2 — Template

      
Generate a starter document to take into Word, Excel, or another tool for product-specific development. This is scaffolding, not a finished BPR.

      
    
        
  • Checklist (plain text) — Printable, with checkboxes, sources, and domain tags. Good for design meetings or verifying that a draft BPR covers all 42 elements.
    • 
        
  • Tab-separated (TSV) — Paste directly into Excel or Google Sheets. Add your own columns for SOP references, responsible parties, or product-specific details.
    • 
        
  • HTML table — Open in a browser, copy-paste into Word. Includes "Present" and "Notes" columns for gap tracking during template development.
    • 
      

      
Toggle Include implementation guidance and Include rationale to control how much context appears in the export.


      
The Compliance Pipeline

      

        Audit
        →
        Workflow
      

      
Use this sequence when you are reviewing an existing BPR for compliance gaps.


      
Step 3 — Audit

      
Perform a gap analysis by comparing a real BPR against the 42-element reference.

      
    
        
  • Fill in session metadata at the top: product name, BPR date, your name, and draft/approved status.
    • 
        
  • Work through each element. Open the BPR you're auditing alongside this tool. For each element, set the status:
          
      
            
    • Present — Fully addressed in the BPR.
      • 
            
    • Partial — Exists but incomplete, ambiguous, or doesn't meet the implementation guidance.
      • 
            
    • Missing — Not in the BPR at all.
      • 
            
    • N/A — Does not apply to this product or process.
      • 
          
    
        
    • 
        
  • Record evidence in the notes field. Be concrete: "Section 2.1.3, but missing verifier initials field" is useful; "Needs work" is not.
    • 
        
  • The progress bar tracks completion, color-coded by finding type.
    • 
        
  • Use Mark All Present if starting from a known-good BPR and flagging exceptions only.
    • 
      

      
All audit data lives in memory. If you close or refresh the page, it's gone. Proceed to the Workflow tab to export, or use Copy JSON in the Workflow tab to save your data externally.


      
Step 4 — Workflow

      
Turn your audit into a formal, timestamped artifact for a document management system.

      
    
        
  • Switching to this tab automatically pulls audit metadata forward (product name, reviewer, approval status). Complete the remaining fields: your title, the BPR document ID, and any approver comments.
    • 
        
  • The report preview updates in real time. It includes an executive summary with counts and a detailed findings table with per-element status, source, and notes.
    • 
        
  • Set the approval status to Draft, Approved, or Needs Revision.
    • 
      

      
Three export options:

      
    
        
  • Print / Save as PDF — Opens the browser's print dialog. The print stylesheet hides all controls and renders only the report. Choose "Save as PDF" for a clean artifact.
    • 
        
  • Download HTML Artifact — A standalone file with all styles inline, no scripts, no interactivity. A frozen record you can archive or upload to a DMS.
    • 
        
  • Copy JSON — Structured data (metadata, summary, per-element findings) for API integration or programmatic processing.
    • 
      


      
Using Tabs Independently

      
You don't have to run the full pipeline. Each tab works on its own:

      
    
        
  • Learn — Reference and training during onboarding, SOP development, or CFR citation lookup.
    • 
        
  • Template — Quick export for planning sessions. No audit data needed.
    • 
        
  • Audit — Gap analysis without generating a formal report. Use JSON export to save work externally.
    • 
        
  • Workflow — Manual report generation if you've already audited on paper. The findings table will show "Not reviewed" for elements not assessed in the Audit tab.
    • 
      


      
Tips

      
    
        
  • Domain colors are consistent across all tabs: red = Regulatory, blue = Industry, green = Data Integrity. During audits, this lets you visually triage: regulatory gaps are compliance risks, industry gaps are quality risks, data integrity gaps are audit risks.
    • 
        
  • The session ID (e.g., BPR-AUDIT-20260410-247) is auto-generated with the date baked in. Replace it with your own document control number if needed.
    • 
        
  • The tool works entirely offline once opened. No external dependencies, no analytics, no data leaving your machine.
    • 
        
  • State is intentionally not persisted between sessions. This keeps things simple and avoids stale data. Export before you close.
    •